Cloud connector deployment guides #3355
Open
+50
−8
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
olegsu
reviewed
Oct 7, 2025
|
|
||
| Cloud connector deployment for integrations allows you to quickly provide Elastic with access to your third-party cloud service provider accounts. This deployment method reduces administrative burden by eliminating the need to keep track of authentication details such as API keys or passwords. Ultimately, cloud connectors are meant to make it easy to manage deployments with many integrations collecting data from CSPs, by providing a simple, reusable means of authentication. | ||
|
|
||
| ## Where is cloud connector deployment supported? |
There was a problem hiding this comment.
It is important to note that to authenticate with AWS we currently require the Kibana to be deployed on AWS as well, otherwise the cloud connector will be shown as an option.
For authentication with Azure we dont require this and any location of kibana deployment is supported.
Below internal diagram emphasis Kibana location and the target CSP.
The two blue boxes (from Azure or GCP to AWS) are in research phase yet.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #2891 by creating documentation for the new technical preview deployment method for the CSPM and Asset Discovery security integrations. This deployment method provides secure-by-default, reusable deployment for cloud service provider (Azure, AWS, GCP) integrations by handling authentication behind the scenes. It uses a different method for each CSP.
The current phase (phase 1) only supports Azure and AWS, and only for the CSPM and Asset Discovery integrations